BBS Toolkit/BBS Toolkit.iso/programs/tb044.zip/TURBOARD.DOC

Text File | 1992-05-29 | 66KB | 1,620 lines

TurBoard v0.40

from Software @ Work

TurBoard Version 0.40 Sysop's Reference Manual
(c) Copyright Shawn Rhoads 1991,92, All Rights Reserved
(c) Copyright Software @ Work 1991,92, All Rights Reserved

May 28, 1992

This document written by Shawn Rhoads

TurBoard is an NAPLPS, ANSI and ASCII asynchronous
telecommunications program designed to provide server E-Mail,
data and information exchange for a group of users.  The system
can be used in a public or private environment and over a LAN or
Modem connection.

If you wish more information about TurBoard and how to register
your copy for $35, contact:

Shawn Rhoads
Software @ Work
P.O. Box 283
Chattanooga, TN 37401-283
[phone] (voice)
[phone] (data)

Unfortunately, time has not yet been taken to write a detailed
specification of the TurBoard BBS System.  This document has
been written to enlighten TurBoard Sysops of the commands they
can use to configure their system.

You can always leave a message on the support bulletin board in
the TURBOARD forum.

TurBoard v0.40 Sysop's Reference Manual

Table of Contents:

1. Requirements  . . . . . . . . . . . . . . . . Page 3
2. Installation Instructions   . . . . . . . . . Page 3
3. Configuration   . . . . . . . . . . . . . . . Page 4
       Changing System Options . . . . . . . . . Page 4
       Customizing Security Levels . . . . . . . Page 5
       Forum and File Security . . . . . . . . . Page 6
       Ads, BBS List, Books  . . . . . . . . . . Page 7
       Doors and Misc Security Menu  . . . . . . Page 7
       FidoNet Security Menu . . . . . . . . . . Page 8
4. Adding and Maintaining Bulletins  . . . . . . Page 9
5. Mail Forums . . . . . . . . . . . . . . . . . Page 9
       Maintaining Mail Forums . . . . . . . . . Page 10
       Chairmanship  . . . . . . . . . . . . . . Page 10
       Security in Mail Forums . . . . . . . . . Page 11
6. File Directories  . . . . . . . . . . . . . . Page 12
       Adding and Maintaining File Directories . Page 12
       Adding Files to Your Directories  . . . . Page 13
       UPLOADS and how they work . . . . . . . . Page 13
7. Doors . . . . . . . . . . . . . . . . . . . . Page 14
8. The YAK Subsystem . . . . . . . . . . . . . . Page 15
9. User Commands . . . . . . . . . . . . . . . . Page 16
10. Classified . . . . . . . . . . . . . . . . . Page 17
11. BBS List . . . . . . . . . . . . . . . . . . Page 18
12. On-Line Books  . . . . . . . . . . . . . . . Page 19
13. Art Gallery  . . . . . . . . . . . . . . . . Page 19
14. Keyboard Commands  . . . . . . . . . . . . . Page 19
15. Colors?  . . . . . . . . . . . . . . . . . . Page 20
16. Full Screen Editor . . . . . . . . . . . . . Page 21
17. Line Editor  . . . . . . . . . . . . . . . . Page 21
18. Command Line Parameters  . . . . . . . . . . Page 21
19. Modem Configuration  . . . . . . . . . . . . Page 23
20. FidoNet! . . . . . . . . . . . . . . . . . . Page 23
       Configuration of TurBoard with FidoNet  . Page 24
       Setting up FidoNet for the First Time . . Page 24
       TBFIDO.EXE  . . . . . . . . . . . . . . . Page 24
       COST and TurBoard . . . . . . . . . . . . Page 25
       EchoMail  . . . . . . . . . . . . . . . . Page 25
21. Customizing Your Displayed Screens . . . . . Page 26
22. NAPLPS Graphics  . . . . . . . . . . . . . . Page 28
23. DAILY.BAT (Daily Batch event)  . . . . . . . Page 28
24. TurBoard Terminal Emulation  . . . . . . . . Page 28
25. Registered TurBoard Sysops   . . . . . . . . Page 29

TurBoard represents a *lot* of work.  Even if you don't
contribute to the shareware cause, we are always looking for new
ideas!  Please support the shareware cause with your input, call
the support BBS (PC Chattanooga, 615/756-7810) and give us your
input!

Requirements

TurBoard requires that you have a PC-DOS session with at least
320 kilobytes of RAM. A serial port, modem and LAN hardware are
optional.  While the serial port and modem are not required to
run this program in local mode, you must have them to run a
bulletin board system!

It is suggested that you use a asynchronous communications
FOSSIL and have DSZ loaded into your PATH.  Other than this, no
other software is required.

If you intend to run a message intensive system, a 2400 baud
modem and about 5 MB of free hard disk space is all that is
required to run a small to modest message based system.  If you
want to add doors, download files, FidoNet echo forums and other
features generally associated with bulletin board systems, it is
suggested that you have a 20 MB hard disk minimum.  There is no
upper limit.

For local NAPLPS displays, TurBoard requires that you have a EGA
or a VGA installed in your computer.  CGA mode can be used with
a device driver from PC Chattanooga, but it is not recommended,
and the poor graphics make it almost unusable.  This, however,
will not hinder your callers from using NAPLPS, you will mearly
see the NAPLPS codes locally in text mode rather than seeing the
NAPLPS images.  (For optimum speed, it is suggested that you
keep local viewing off via the Alt-S)noop command anyway.)

Installation Instructions

Ensure you have a copy of DSZ (file transfer program) and it is
included in your current path, TurBoard requires this.  Also,
you should have a FOSSIL loaded, I suggest using X00.SYS.  You
can install X00.SYS in your CONFIG.SYS with the statement
DEVICE=X00.SYS.

UnZip the file TB???.ZIP in the directory you wish TurBoard to
reside.

! Save a copy of TB???.ZIP, as some of the files will be removed
(the ZIP's) after they are used by the INSTALL program.

1) To configure your TurBoard system for the first time, simply
type:

  INSTALL

The correct subdirectories will be created and zip files will be
unzipped (make sure that your PKUNZIP program is in the current
path).

2) Once the INSTALL program has successfully run, you will be
prompted to start TurBoard by entering the following command:

  TB

3) If this is the first time you have dealt with TurBoard,
choose the Q)icksetup option.  TurBoard will create all the
subdirectories it needs and you will only be prompted for
hardware specific information.

When configuring your modem, you should see a configuration
option similar to your modem.  If not you may use the modem
configuration strings included in a later chapter to help you
configure your particular modem.

Always use TB.BAT!  This is how you should always start the
TurBoard BBS system.  If you do not, the system will stop
whenever someone enters a door or downloads a file.

Answer the questions.  If you have a problem configuring your
modem, (you do not get the "Waiting . . ." status after you have
configured everything,) we may need to set up a special modem
definition for your specific modem.  If this is the case, call
the TurBoard Support BBS system (PC Chattanooga) at 615/756-7810.

The following two files will be unzipped in the TEXT and YAK
subdirectories of the same name.  They will be deleted when
INSTALL runs, but you may want to install them yourself.  They
are described here for your information.

TEXT.ZIP  - Includes Help Files, Welcome, and Logoff Screens.
YAK.ZIP   - Includes the menu files, news files, and the yak
data files.
              (more on this later)

After this you may delete these ZIPs, you will no longer need
them all the other files are created automatically as they are
needed.

Configuration

Once you are at the call waiting screen, you will probably want
to customize your system to reflect the BBS name, open or
closed, etc.

To log on for the first time, type Alt-L for local login.  Give
the name and password you specified when you installed TurBoard.
 When you see the ">" symbol, this is the primary TurBoard
command prompt.  Any command may be entered whenever you see
this prompt.

Enter the "SE" (for setup) command and choose option 1.  Now you
may change your system name and some other parameters.  To
change how your system displays news and other options, you may
wish to read "The YAK Subsystem" section below.

You will see a menu containing options to customize system
information, security levels, forum and file security, ads, BBS
list and book options, doors and misc. options, FidoNet options
and security and modem settings.

Following are some guidelines for configuring these options.

Changing System Options

You are already familiar with the SE command.  Option 1 allows
you to change some of the primary system settings.  They are
explained below:

Name - This is the system name (ex: PC Chattanooga) that you
wish to refer to you BBS system as.  Setting this option will
cause your system name to appear throughout the system menus,
such as the file directory screens.

Password - If you desire, you may require a logon password for
EVERYONE to use every time they log on.  Some Sysops desire a
private board, but one you don't have to be pre-registered to
log into, this is a method to accomplish that.

Sysop Password - For added Sysop access security, this option
will require all users with Sysop access to enter this password.
 This is good if your Sysops use their password on another
system.

Sysop Avail - Toggles the message the user gets when O option is
used.  Same as Alt-O at the keyboard, but allows the Sysop to
turn this option on and off remotely.

Sound - If this option is turned on, the BBS will beep (ASCII 7)
when the user does.  This is defaulted to off.

Zone - Used to specify the primary FidoNet zone of the BBS.
Normally 0 for a non-FidoNet system.

Net - Used to specify the primary FidoNet network of the BBS.
Normally 0 for a non-FidoNet system.

Node - Used to specify the primary FidoNet node of the BBS.
Normally 0 for a non-FidoNet system.

Point - Used to specify the primary FidoNet point of the BBS.
Set this option to 0 for a non-FidoNet, or a primary node system.

Total Callers - How many people have called the BBS to date.

Open System - Normally yes, this option can disallow new users
tolog on.

Time Zone - Specifies which time zone the BBS resides.

Log Records - Specifies how the system log is kept.  If None,
then no monthly files are kept of the user activity.  Set this
option to 1 for monthly files.

Customizing Security Levels

The TurBoard security levels can be customized by choosing
option 2 from the SE command.  You can add new security
definitions as well as change names and time limits on currently
defined levels.  You can enter colors at the command input line,
but you will need some additional information, refer to the
"Colors?" section below.

Forum and File Security

These are security levels generally associated with options for
message forums and file directories.  The are modifiable so that
certain privileges may be given and removed from different
security classes.

Add Forum - This security and higher has the authority to add a
new message forum.  He may not, however automatically be able to
use the CH command on that forum!

Edit Forum options (CH command) - This security and higher has
the authority to issue the CH command in any message forum,
regardless if he is the actual forum chairman or not.

Delete Forum - This security and higher has the authority to
remove any message forum with the DF command.  (The actual data
files must still be manually deleted.)

Enter FidoMail - This security and higher may enter FidoNet
messages in a (the) message forum designated as FidoNet.
Persons with security levels below this specified level may only
enter "normal" messages into the forum.  (Which do not get
routed into FidoNet.)

Read all mail - Probably should be named "read private mail".
This person may read ANYTHING, including all message forums and
all private mail in those message forums.

Move Message - Security required to issue the MM command which
moves a message from the current forum to another forum.

Add File Directory - Security required to add a new file
directory.  (colors may be used as in naming of security levels.

Delete Directory - Security required to remove an <empty> file
directory.

FF (or Find Files) - This command will search all your
directories and add any new files in those directories.

Edit Directory Entry - This is the security required to edit a
FILE ENTRY, not a directory entry (which may not be edited once
created.)

Edit Extended - Allows access to extended file entry functions
including resetting the review of the file as well as editing
the comments file.

Ads, BBS List, Books Security

This menu (option 4 in the setup section) deals with securities
for the classified ads, BBS list and Books subsystem.  For
additional information on each of these, please refer to the
appropriate section.

Delete Ad - This security and higher has the authority to read
and delete ANY classified ad.

Ad categories - This security and higher has the authority to
alter the characteristics of any ad category.  This includes
security levels, etc.  (see the section on classified ads.)

Delete BBS entry - Authority to delete BBS entry.  The only time
a user may delete an entry but not have the required security
level is if they were the one who entered it in the first place.
 In case you want the users to have Delete access all the time,
lower this option to the security you prefer.

BBS Sysop Info - Shows detailed information about Sysop's home
address, etc.

Make BBS text - Security required to created the actual BBS text
file that you may or may not want to issue every month.

Add BOOK - Required security to add a new book.  (see section on
books for more details)

Edit Chapter - Required security (if you are not the "author" of
a book) to edit a chapter in the book.

Add chapter - Required security (if you are not the "author" of
a book) to add a chapter to the book.

Add bulletin - Required security to issue the AB command which
creates a new bulletin.

Delete bulletin - Required security to issue the DB command
which removes a current bulletin.

Edit Bulletin - Required security to issue the EB command which
edits a current bulletin.

Enter Resume - Required security to enter a resume into the
classified ads system.

Scan Resume - Required security to scan resume's in the
classified ads system.

Doors & Misc Security Menu

This section (option five in the setup menu) deals with security
levels for on-line doors and other special command line options
including the YAK subsystem, which controls things such as the
on-line news and the main menu.  You can customized the system
to your preference, and this menu sets up the security levels to
do so.

Add Door - This is the security required to issue the AD command
to set up a new external door.

Edit Door - This is the security required to issue the ED
command used to change the options of a door's setup.

Edit Text Files - This is the security required to issue the
EDIT command at the > prompt.  The EDIT command requires that
you include a parameter on the line indicating the path and
filename of the file you wish to edit.  (For file names with no
extension, be sure and include a period at the end.  Ex: > edit
shawn.  )

Type Text Files - Security required to issue the TYPE command at
the > prompt.  This is useful in displaying a file you just
edited witht he EDIT command.  A file name parameter is required
here also as well as the same period naming convention (see
above).

Detailed Log - This is the security required to see a log
including anything other than the (1) logon action.  For more
information see the Log section of the manual.

Edit Users - This is the security required to edit any user
other than yourself, (and to edit some normally uneditable
options on your record.)  Normally reserved for Sysops only.
Also, all passwords will be visible by this security level.

Yak Subsystem - This is the required security to initiate the
YAK subsystem editor.  (YAK is the command.)

Setup Menus - This is the security to start these setup menus.

Upload SL - This is the security level required to upload files
(use the U command).

New User SL - This is the security level assigned to first time
callers.

FidoNet Security Menu

This menu contains some configuration options for FidoNet.  Some
ofthem are for debugging problems that may exist in FidoNet,
others are just for looks.

Set NetMail Ctrl - This is a debugging tool used to see the
operation of the SEEN-BY, ^aPATH and other lines, in case there
is a routing problem with one of your FidoNet Echos.  (This
options will cause problems if you are sending mail down the
line to another system, please use with caution!)

EchoMail origin - This is that famous " * Origin: " line that
everyone is so cute with.  You may enter anything here, but
preferably your system name and location.  "(net/node)" will be
automatically appended on the end.

Point Network - If you have a point network, specify it here so
that mail will be properly routed to your points.

Allow Passthrough - Probably should be named, "allow leech".
Tells TurBoard to take mail that was not addressed to you, but
to someone else, and send it.  (This may or may not be a long
distance call.)  This is only for NetMail, not EchoMail.

Adding and Maintaining Bulletins

It's a good idea to put important information for your users in
bulletins so they can refer back to the information as often as
they need to.  Bulletins are controlled solely in the TurBoard
environment.  You never need to go outside the system unless you
wish to import data or text from another source.

Initially, TurBoard has no bulletins.  If you wish to create
one, you will need to use the AB command.  Once you issue the AB
command, you will be prompted for the description of the
Bulletin.  This is the text that will appear in the main
bulletin menu.

Once you've entered the description, you will enter the editor
(either full screen or line, depending on your setup).  Here is
where you will enter the actual bulletin text.  If you are in
the full screen editor, you can enter colors with the Ctrl-W
command.

After the bulletin is saved, you will be prompted for the
security level of persons with access to the bulletin, as well
as a read flag.  This flag displays "No" or "Yes" depending if
the person has read the bulletin or not.  (It does require some
file space, but only 1 bit per person, very small.)

For example, lets create a new bulletin via the AB command
entered at the TurBoard prompt:

> AB <enter>

You will notice that you are now creating a new bulletin.

Some there are some special files you can place in your bulletin
directory to add NAPLPS support that will override the normal
TurBoard displays.  Using this technique, you can create a
customized bulletin display that will take full advantage of
NAPLPS.

If you wish to create your own bulletin menu in place of the
normal TurBoard created menu, create a file called BULLN (for
NAPLPS), BULLG (for ANSI) or (BULL) for ASCII and place it in
the DOS directory named TEXT (under the TurBoard root
directory).  It is the System Operators responsibility that the
BULL? file matches the information that TurBoard knows.

In addition, you can create specific emulation files for NAPLPS,
ANSI and ASCII.  The name of the file is BUL[bulletin
number][Emulation code] with no extension.  For example, if you
wanted to add a NAPLPS frame for bulletin number 3, the name of
the file would be BUL

Mail Forums

The basis for any bulletin board or other telecommunication
program is the ability for users to communicate with one
another.  I've attempted to make TurBoard as communications
intensive as I could.  While some packages refer to message
forums as "bases," "areas" or "conferences."  I choose "forum"
because that is what messaging should be:  a forum for
discussion!

In any case, TurBoard allows unlimited message forums
(limited,rather, by your available hard disk space).  I choose
names rather than numbers to give a more human feel to each
forum (and if a BBS has 200 forums, who knows what #132 is?)  I
am, however, considering switching to a number format if there
are enough requests.

Create the message forums with the AF command (standing for Add
Forum).  The first forum you create is very important!  It is
the all time default forum.  I choose to call mine "PRIMARY".
Unless another forum is joined first or someone reads all the
messages and automatically joins the next forum, messages
entered with the E command get sent to this forum.

The primary message forum will always be displayed at the top of
the forum list.  Everything below that is sorted in alphabetical
order.

These are the TurBoard message commands that are active when you
are reading mail.  These commands are meaningless unless the P,
R or S command is active.

Maintaining Mail Forums

Usually, there are no requirements placed upon the Sysop for
maintaining the message forums.  And assuming you had unlimited
disk space, everything would be okay.

But, for networking reasons, when messages are deleted, they are
NOT removed.  They are  flagged for deletion until some process
(currently the sysop only, but events are planned) comes along
and physically removes them.

The PM (for pack messages) is a local forum command that removes
all messages flagged for deletion as well as all private mail
that has been read.

Another problem that Sysops run into is messages entered into a
forum that really belong somewhere else (like in the primary
forum).  The MM (for move message) command will copy a message
to the specified forum and flag the original message for
deletion.

Conference Chairmen have the ability to PM and MM in their
respective forum (and only in their respective forum).

Chairmanship

It is profitable for everyone when you assign a leader or
"Chairman" to a forum.  People can identify him/her with the
forum topic and have a direction to ask questions and enter
comments.  The Sysop benefits by not having to police every
forum and allowing the Chairman to pack and move messages.

Chairmen have the power to read private mail, delete and
undelete any message in their forum.  Chairmen also have the
power to set the security level required to read/enter messages
as well as changing the description line for the conference via
the CH command.

Chairmen can also assign away their chairmanship.

There are several things that a chairman (as well as the Sysop)
has control over.  They include how many messages should remain
active at any given time, how old messages can be before they
are deleted, if people can enter private mail in this forum,
what security levels can read or enter mail in this forum, and
the description of the forum (displayed in the forum menu.)

Message Forum Security

Security is also defined by the CH command.  Version 0.36 and
above have special security "groups".  The security level for
each message forum can be set as always with a "security level
>= X" where X is a security level set by the Sysop.  A new
edition will allow up to four exact security level matches as
well.  These are defined as "secuirty level = X" where X is a
security level set by the Sysop.

For example, if a Sysop has defined security level 35 to be
"Macintosh Users" and 40 to be "Amiga Users" and 50 to be "DOS
Users" and wishes only "Macintosh Users" and "DOS Users" to
access the "Windows GUI" forum, security can be set as follows
(via the SE command, set security level).

Security Level >= 200   (All levels >= 200 have access)
Security Level = 35     (Give Macintosh Users access)
Security Level = 50     (Give DOS Users access)

Up to four specific "exact" secuirty levels may be defined.
This method gives greater flexability than pervious "group"
methods, as the entire BBS is not limited to a certain number of
"groups".  Access, however, may only be given to a maximum of 4
specific security levels and one greater than or equal range of
security levels.

Also, in the case of FidoNet forums:  A user with security
greater than or equal to the enter security for that forum may
enter normal messages.  BUT, if that user attempts to enter or
reply to a FidoNet message, their security level must exceed or
be equal to that of the security level set tin the SE option for
entering FidoNet messages.  That is to say, a FidoNet (not Echo)
message can only be sent if the security of that user is
authorized.

Every forum may have a initial screen displayed when you first
join it.  This is useful in showcasing the forum for first time
joiners, so they will get an idea of what the forum is about.

File Directories

File directories in TurBoard are used to catagorize files into
different interest groups.  In reality all the files
descriptions are stored in one file (this may prove to be a
problem with large networks).  A separate file contains
information on the "directories".

When a file belongs to a directory, it is specifying where it
resides on the BBS system physically.  In addition it is giving
a general description of what the file does/is.  Please do not
manually move files, as TurBoard attempts to keep up with where
that file is on the system.  If you move files around outside of
TurBoard, the system will get confused and may not operate
properly.

Adding and Maintaining File Directories

Adding a new file directory is easy.  Use the AF (Add File
directory) command to specify a name for the directory, path on
the disk drive, and description.  The name is of little
importance, but you should note that the directory menu sorts
the descriptions based on your directory name.

For example:

UPLOADS   Recent Uploaded Files (Always use UPLOADS with an S!)
DOSGAMES  DOS Game Programs
DOSGRAPH  DOS Graphics Programs

Will appear as:

1] DOS Game Programs          2] DOS Graphics Programs
3] Recent Uploaded Files

This is useful when you want to group like directories together.

Another function you should be aware of is the FF command.  This
command will scan all of your disk drive directories specified
in the file descriptions for new files.  If one is found, it
will prompt you for information about that file.

To list the files you currently have on-line, use the F command.
 You will see the file directory menu, and at this point you may
choose a number or type in a search keyword.  For example, you
may type DOS and GAME to get files that match those keywords.

Adding Files to Your Directories

The easiest and best way to add files to your directories is to
upload them while locally logged on.  For example:

First, you must have an upload (UPLOADS) directory, if you are
not sure, read the section on uploads below before continuing in
this section.

While you are locally logged on (either by ALT-L or the DOS
command "turboard -l") use the U command (for upload file).  You
will be prompted for a path and a filename.  Give TurBoard the
path and filename of the file you wish to upload, and it will be
added to the upload directory.

Once the file is added, display it with the N command.  Choose
the number of the file you just uploaded, and then choose the
option to move the file.  At this point, you may place the file
in any directory you see fit.

To add a lot of files at once, copy the files (at the DOS
prompt) into the physical directory you wish to add them to.
Log back into TurBoard and use the FF function.  Enter each
description of the files.  Verify the files were added by using
the f command and listing your directory.

Once a file is added, ALWAYS move it with the TurBoard move
command, otherwise the File Listing will not have correct file
location information.

UPLOADS and how they work

There is no rule governing how the file directories should
appear except one:  In order to receive uploaded files, the
Sysop needs to create an UPLOADS (with an S!) file directory.
This directory says that all uploaded files will be placed in
this directory, otherwise they go to the root file directory.

When a file is uploaded (or placed in the upload directory and
FF function used), you will be asked for a one line description
of the file.  Following that, you will enter the full screen
editor where you will be tempted to write a paragraph or two on
the file.  This is purely optional, you can abort the edit and
continue on.

There is a text file that is displayed whenever the U command is
issued.  It is called UPLOADS.TXT.  If you have used the default
subdirectories, use the command:

> edit text\uploads.txt

You can include TurBoard colors and text to be displayed,
formatting is automatic.

There are additional special directory information files that
you may want to create.  These files are keyed to the search
keywords or directory names and have the extension .FXT.  For
example, you can create a UPLOADS.FXT file in the TEXT directory
to display whenever someone lists your most recent uploads.  If
someone enters the command "F ALL" TurBoard will check to see if
there is an ALL.FXT file in your TEXT directory, and if so,
display it along with the complete file listing.  Other examples
are "F GAMES" for GAMES.FXT or "F 3" for the directory name for
#3 with an .FXT extension.

Doors

A "doorway" or "door" (once called a "window") is actually an
external program that the bulletin board software passes
complete control to.  This is generally a game (likeTradeWars or
Solar Realms) or some useful information, like a BBS list or
Bible Trivia Game.  It is TurBoards responsibility to initialize
any information files that the door requires.

TurBoard uses the AD (add door) and CD (change door) command to
maintain the door system.  Doors can be entered with the DO
command.  In order for doors (and up/downloads) to work
correctly, TurBoard must be started with the TB.BAT file,
otherwise, when a user enters a door, it will drop to DOS and
processing will stop.

Doors are by far one of the hardest things to install, simply
because there is no specified standard by which they work.  Each
one is different and therefore a challenge, I'm afraid to say.
There are several questions you will be asked that TurBoard uses
to try to talk with a door.  These are:

Name - The 1-8 character name you choose to give your door.

Description - A 60 Character description of the door contents.

Path - The physical path of the door (this may be specified from
the root TurBoard path, i.e. DOOR/SOLAR is the name of
C:\TURBOARD\DOOR\SOLAR, if C:\TURBOARD is your root TurBoard
path;the path you are in when you start TurBoard.)

Command - the DOS command to start the DOOR, usually a BAT file.
 This BAT file should exist in the directory you specified in
the PATH option.

FileType:  Currently, only one file type is supported.  It is
TurBoard type 1.  Specifing type 1 tells TurBoard to put a
DORINFO1.DEF file in the directory specified in the PATH
parameter.  Please set up your door to look for DORINFO1.DEF
there.

ANSI - If this option is true, the user must have ANSI graphics
turned on before entering this door.  This helps cut down on
ASCII users starting something they cannot finish.

NAPLPS - If this option is true, the user must have NAPLPS
graphics turned on before entering this door.  This helps cut
down on ASNI below users starting a NAPLPS graphics door.

Security - The minimum required security level of the user
starting the door.

Delete this entry - option to delete this door record.

The YAK Subsystem

YAK really doesn't stand for anything other than "to talk,
probably more than one should."  In any case, the YAK subsystem
in TurBoard is where specialized information such as logon news,
mail notifications and even the main menu come from.

To start the YAK subsystem, type "YAK" at the TurBoard prompt.

To use YAK requires that you understand what you want to happen.
 For instance, if the first thing the user sees is the logon
news, the NEWS information should come first.

These are the current checks, and YAK supports 4 different
checks at a time.  These are the criteria that must be met
before a message (text file) is sent to the user.

For example, the main menu should be the last item in your YAK
list.  It should use only 1 check value (number 9).

In case 5, the X value is an internal TurBoard (DOS, actually)
format.  To use the integer for exactly the point in time you
are entering the information, use the NOW keyword.  This will
insert the DOS date/time stamp for that point in time.

Whenever TurBoard is finished processing, it checks the YAK
List, it goes through each item in the list to see if that item
meets all the criteria.  If so, TurBoard displays the file
associated with that information and sets the different yes, no
and blank response information.

Perhaps you want the BBS to ask a user if they want to read
their mail now, if they have mail waiting.  This can be done
with the YAK subsystem as follows:

Make a new YAK entry:

Display file:  MAILNOW

Check1: 1
Checkval1: 0
... [leave the rest of the checks as default]
Yes Responce: P  (the command to read your personal mail)
No Responce:
Blank Responce:

Using your TurBoard editor or the YAK option to edit the
MAILNOW.YAK file.  Ex:  EDIT YAK\MAILNOW.YAK.  It should read:

You have new mail waiting, do you wish to read it now?

User Commands

Following commands can be entered at the > prompt.  Most of the
two letter commands require extended access.

? - Help with the currently executing operation.
A - Art Gallery - Shows various ANSI and NAPLPS
displays.
B - Bulletins
C - Classified Ads - Enter/ read/ scan classified ads.
D - Download File - Receive a file from TurBoard into your
system.
DO - DOOR menu - Run an external program from TurBoard.
E - Enter Message - Send a message to another user or to the
general public.
F - File directory List - List files available for download.
G - Good-bye (log off) - Leave this TurBoard system.
H - Emulation Toggle - Change to ASCII, ANSI or NAPLPS mode.
I - Inquiry (history) - Show caller history.
J - Join Mail Forum - Join a message forum (usually by subject.)
K - Delete message - Remove the message you just read.
L - BBS List - List BBS systems on-line.
N - New Files - List new files since you have last logged on.
O - Operator page - Page the operator for a "chat" session.
P - Personal Mail - Read mail that has been flagged for you.
Q - Display the Main Menu - Go back to the main menu.
R - Read Mail - Read messages in the current forum.
S - Scan Current Forum - Scan messages in the current forum.
T - User List - List the users who are active on this system.
TIME - Displays day, time and time remaining.
U - Uploads - Upload files to this TurBoard system.
V - Version - See the version of TurBoard this system is using.
W - Who's on - See the other people signed onto this TurBoard
X - eXpert toggle - Put your session in Xpert mode.
Y - Your information - Review and change your user account
information.
CH - Chairman Utilities - Change forum defaults information.
Chairman or Sysop access.  Allows the assigning (or assigning
away) of chairmanship, setting of certain forum options.
AM - Add Mail Forum - Starts a new message forum and adds all
the associated information.
DM - Delete Mail Forum - Deletes a message forum (data files
remain intact, you must physically, ie via DOS, remove the files
in that subdirectory).
MM - Move message - Moves a message from the current forum to
another specified forum.
PM - Pack Message Forum - Deletes messages that have been
"deleted" and private mail that has been read.  Removes data
files and header records.
AF - Add new file directory - Will add the file forum and
include it on the forum choice list.
DF - Delete file directory - Remove an empty file directory from
the directory menu.
FF - Fix File Information - Will search all the file storage
directories for new files not included in the list and add them
(you must type in the descriptions).
YAK - YAK subsystem
TYPE - print specified text file
EDIT - edit specified text file
COPY - copy a file from one DOS location to another.
DIR - Give a directory of the specified DOS directory.
AD - Add new DOOR - This command will add a new door (be sure
you know what you're doing!)
CD - Change existing DOOR - After a door has been added, you can
change the setup with this command.

Classifieds

The Classified feature of TurBoard is not a standard bulletin
board feature.  It's function is to provide a place for the
buying and selling of goods through the public (not retail).

Most bulletin boards will include a "For Sale" forum to
accomplish this function.  I found that this was difficult for
people to use because it didn't organize the information in a
way people could easily get at it.  They are required to scan
the subject of every message and pick the one's they are
interested in.

This will work okay so long as there are only a few ads to scan
though.  So I thought to myself, "What do people normally use to
buy and sell items?  Classified ads!"  So I decided to implement
an "electronic" version of the classified ads.

I have included a rather detailed category file (in TBADS.ZIP on
PC Chattanooga 615/756-7810) that is based on the Atlanta
Journal/Constitution.  Of course, you can create your own, but
it's tedious!

You may add new classified categories with the C command.
Simply choose the "Add new category" option.  Other than this,
the system is completely self maintaining.

BBS List

This is a fairly standard BBS feature.  There are some doors
that perform the same function available.  The advantage to the
TurBoard BBS List command (L at the main prompt) is the ability
to comment and review each BBS entry individually.

The BBS List also does not require any maintenance on the
Sysop's part.

Once you choose the L command, you have several options.  A
complete BBS list, a local BBS list, add a new BBS entry or
create the BBS text file.

The difference between the complete and local BBS list is the
"Is this BBS a local call?" flag.  Only those that answered yes
are displayed in the local BBS list, thereby eliminating toll
call BBS's.

To add a new BBS entry, you can accomplish that one of two ways.
 You may use the ADD command while displaying the entire BBS
list, or you may simply choose option 3.  If you use the ADD
function, you will see the BBS inserted in the list as you are
listing it, so you can ensure that it was indeed added.

Option 4, create the BBS text file, is an option you can use to
publish your BBS list.  It will create a text file with two
sections, a short BBS list and a detailed BBS list.  Before the
first section the file "BBSLIST.TXT" will also be included from
the text file path.

If you wish to edit this file, and you have used the default
path names, use the command:

> edit text\bbslist.txt

After you have edited the file, save your changes and it will be
included in your next BBS text file creation.

On-Line Books

Some BBS programs refer to features similar to this one as
"continuous story" or "book writer".  I had planned to include
an option for on-line databases, but due to the request of one
of the users of PC Chattanooga, I added support for a
"continuous story" as the initial implementation.

The idea here is to have entertaining, technical or whatever
kind of information available for users to access on-line (with
the option to download all or parts of the information).

In addition the users may add to the information as they feel
nessessary.

Options are planned for keyword searching, downloading,
uploading, etc. of the books.

To enter the book option, type the command:  BO

From this point you will be able to enter/delete/add to books
and chapters of books.  Each book may have an "Author"
associated with it.  This is sort of like the Chairmen in the
message areas.  Editors can control, add and delete the chapters
in their book.

Each book consists of multiple chapters.  Each chapter is either
"open" or "locked".  An open chapter allows users to append to
the end of it.  For example, they may continue the current story
or add information to a technical document.

There may become a time when the Author decides that a chapter
is complete, and wishes to stop the extensions on it.  The
chapter may be locked via the edit chapter option (after a
chapter is read).  This will disallow further additions to the
chapter.

Art Gallery

Version 0.40 and above are equipped with an Art Gallery.  This
is a method for displaying ANSI ASCII and NAPLPS frames as works
of art or to demonstrate a terminal emulation like NAPLPS.

In order to add a work of art, use the AA (for Add Art) command.
 To edit the information used to display a work of art, use the
EA (Edit Art) command.  And to display works of art use the A
(Art Gallery) command.

There is an added command called DEMO.  This will rotate between
works of art with a specified period of time.  The rotation will
include all the works of art regardless of current terminal
emulation.

Keyboard Commands

Alt-S  Snoop Mode Toggle

Snoop mode should be OFF anytime you don't wish to monitor the
BBS caller.  Screen writes can slow the output data stream to
the caller, so to increase your BBS's performance, turn snoop
mode OFF at all times.

Alt-T  Chat mode on/ Terminal Mode

To answer a sysop page, use the Alt-T command.  Also, from the
call waiting screen, Alt-T will put you in a full
ASCII/ANSI/NAPLPS terminal emulation.

Alt-O  Operator available Toggle

This toggle the ability of your users to page you.  Turning
sysop page on will allow the BBS users to call you for a chat
session while they are on-line.

Alt-X  Exit

Exit the current operation.  If at call waiting screen, exits
TurBoard.

Alt-I  Information

Gives information on registering the TurBoard BBS package.

Alt-L  Local log on

Used from the call waiting screen to log on the BBS locally.
Name and password is required for security.

Colors?

Turboard uses single ASCII characters to indicate different
colors, you can take advantage of this in the editor and input
prompts.

In NAPLPS mode, TurBoard assigns the following colors to the
internal TurBoard format for cross-compatibility.

To enter these numbers in manually on a line (the file directory
description prompt, for example), use the alt key.  While
holding down the ALT key, type the 3 digit number on the numeric
keypad and then release the ALT key.  At that point the color of
the text you type will change.  TurBoard treats this character
as a full character, so if you make a mistake, be sure to
backspace as far as you can go before trying again.

Full Screen Editor

The full screen editor work with WordStar commands.  If you are
logging on remotely be sure to use doorway mode to get maximum
function from your keyboard.  F1 or Ctrl-H for additional help.

Colors are stored in TurBoard format (see colors above) but in
the full screen editor do not take up a character of space.

Line Editor

The line editor in TurBoard works as most BBS line editors.
Wordwrapping is automatic, and when you are finished editing,
hit return on a blank line.

You will be prompted to Continue, Abort, Quote or Save.  If you
are replying to a message, you may quote by choosing line number
in the message you want to quote.

Colors are not supported in the Line editor.  (Quoting will
still have the highlighted ">".)

Command Line Parameters

There are certain command line parameters that will allow
TurBoard to operate in a networking/FidoNet environment.

These are:

#  -  Node number
(defaults to 1)  Ex: turboard 2
-l -  Local Switch

This switch will bypass the call waiting screen and go directly
to local log on.  For example, if you are in a networking
environment, you can use this switch at program startup, so that
the network node will begin at logon.

Ex: turboard -l

-fd -  Front Door Active

This switch is used when using a front door processor, such as
BinkleyTerm or Front Door.  It will cause TurBoard to check for
a carrier detect, as well as to fall back to DOS after logoff.
(The call waiting screen in used in this mode.)

Ex: turboard -fd

-p##### - Incoming port rate

This switch is generally used with the -fd switch so the front
door can pass the port rate to TurBoard.  The modem to remote
CONNECT rate my not be the same as the Modem to DTE PORT rate.
If this parameter is specified, TurBoard will communicate to the
modem at this rate.

-b##### -  Incoming call baud rate

This switch is generally used with the -f switch so the front
door can pass the baud rate to TurBoard.  An example of the
Batch file that might be used is:

(%3 contains the baud rate parameter)

turboard -f -b%3

-cbios - Use BIOS for NAPLPS writes.

If you experience "snow" or unexpected results on you NAPLPS
displays, you may want to try this switch, it will tell TurBoard
not to use direct EGA and VGA hardware writes and to go through
the BIOS instead.  On the downside, turning this switch on may
cause you to lose characters when in TurBoard Terminal Mode.

-t### - Max Time allowed

This parameter can be used to limit a BBS visit's time limit (in
the case of an upcoming event).  This parameter is usually
passed from some kind of front door processor.

%4 contains the time limit.

Ex:  turboard -fd -b%3 -t%4

Modem Configuration Strings

The following strings may be used to help configure TurBoard.
Use the one that most closely matches your computer.  (You may
refer to your modem manual for additional information.)

Modem Init String

Hayes 1200:  ATS0=0M0S2=1X1H0E0
Hayes 2400:  ATS0=0M0S2=1X1H0E0
Hayes 9600 V.42:  AT&F&K0&C1&D2S0=0S2=255M0E0H0
Hayes ULTRA:  AT&F&K0&C1&D2S0=0S2=255M0E0H0W1
USR Dual Standard:  AT&F&B1&C1&D2S0=0S2=255M0E0&WH0
(USR HST, I haven't tested...)

Terminal Init String

Hayes 1200:  ATE1M1
Hayes 2400:  ATE1M1
Hayes ULTRA:  ATE1M1L1
USR Dual Standard:  ATE1M1L1

Use the standard response codes (check your manual for exact
spelling).

Ex:  RING, CONNECT, RINGING, NO CARRIER, BUSY, NO DIAL TONE

If you have any configuration strings that I have not mentioned
here, be sure to leave a message on the support BBS!

Common Questions on Modem Configuration:

When I start my system, it gets hung in a loop trying to log
itselfon and off.  What's wrong?

The problem lies in the modem configuration.  TurBoard will jump
to the terminal emulation prompt if it thinks there is someone
on-line.  Most modems can configure the Carrier Detect pin (CD)
to follow actual carrier detect or not either by switch settings
or an internal command (USR uses &C1.)

You want to set your modem up so that Carrier Detect follows
actual carrier detect.  (If you do not have switch settings, add
the command to the end of your modem initialization string via
the SE command.)

When someone tries to log off the system, they just get put back
at the start-up prompt again, or the BBS just sits there.
What's wrong?

A high to low signal in the (Data Terminal Ready) DTR needs to
be set to cause the modem to hang up the line.  Most modems use
a switch setting or AT command to control this feature.  (USR
uses &D2.)  If you do not have switch settings to control this
feature, add the command on the end of your modem initialization
string via the SE command.

FidoNet !

FidoNet is a worldwide network of bulletin board systems which
communicate to each other through message "packets"  TurBoard
v0.33 and above will interface with any other FidoNet or
compatible system through a front door.  A front door is a
program which answers the incoming call, decides if the caller
is another FidoNet system or an actual user, and either receives
the FidoNet package or transfers control to the BBS system
(TurBoard).

TurBoard v0.33 includes all the files nessessary to configure
FidoNet with a front door processor.  This includes the
"scanning/tossing" of incoming and outgoing messages.  This is
performed by the TBFIDO.EXE program.  This program will convert
the incoming FidoNet messages to TurBoard format and put them in
their proper message forums.  It will also export messages
entered in the TurBoard forums and put them into FidoNet
"packets".

Configuration of TurBoard with FidoNet

The hardest part about interfacing with another external program
is configuration.  TurBoard has been extensively tested with
BinkleyTerm, and I would suggest using that software.  Included
is a text file called BINKLEY.CFG.  This file contains an
example BinkleyTerm configuration file.  There is also a .BAT
file included (TBFN.BAT) that should be used to initialize
TurBoard when running FidoNet.

It is your responsibility to ensure that the nodelists and other
data that BinkleyTerm requires is configured correctly.

When you are running FidoNet, start the TurBoard system with
TBFN.BAT rather than TB.BAT, this will run the message packer
and automatically start BinkleyTerm.  I would suggest
configuring BinkleyTerm to match the ErrorLevel operations used
in TBFN.BAT.

Setting up FidoNet for the First Time

Actually, TurBoard is about ready to receive FidoNet message
strait out of the package.  Most of your time will be spent
setting up your front door processor (which can be trick if you
are not programmer inclined.)

To set up TurBoard for FidoNet, you will need to specify your
address in the SE menu.  You will also need to set up one of
your message forums as the primary FidoNet forum.

To setup the FidoNet forum (which can be any forum other than an
echoed forum), join the forum you wish to use.  (If you do not
have any forums defined yet, use the AM command first and then
join that forum.  But remember, the first forum you create will
be your master message forum, so you may want to name it
something like "PRIMARY" and then add a new forum for FidoNet,
which you may want to name "FIDONET".)

Once you are in the forum you wish to use for FidoNet messages,
issue the CH command and choose the option for Mail Type (it
will currently say:  "Normal").  Change this setting to F for
FidoNet.  At this point you are ready to go.  Any messages
designated with an address in this forum will be placed in the
FIDOOUT directory for processing by the front door.  It is your
responsibility to ensure that the address on the message is
correct.

TBFIDO.EXE

This program serves three functions.  First, it scanning the
incoming FidoNet directory and converts that information into
useable information by TurBoard.  Secondly, it checks the
outbound FidoNet packets, if it finds ones marked .ECHO, it
combines them into "ArcMail" which are nothing more than FidoNet
compressed packets with the ARC.EXE utility.

Thirdly, if the -p command line parameter is specified, the
program will scan and pack all of the active TurBoard message
forums.  This is complete and automatic.  The settings for the
compression are set with the CH command in the TurBoard system
itself.

FidoNet COST and TurBoard

Cost of messaging is very important to most FidoNet sysops.
Currently, TurBoard does not keep track of how much a message to
a certain system will cost, or even if the target system exists.
 For this reason, it is important that you configure your front
door processor (most likely, BinkleyTerm) when it can and cannot
send messages to different systems.  This is performed with
theBINKLEY.EVT file.  Here you can specify the cost of a message
that is allowed to be mailed.  (BinkleyTerm will check the
Nodelist for an entry and figure the cost from that list.)

EchoMail

TurBoard can handle echomail.  To configure where outgoing (and
incoming) messages are going, as well as the name of the
EchoMail area, use the CH command for your particular forum.

For example:

Once I have set up my system for FidoNet, I perform the
following:

Say I wanted to set up an EchoMail forum with PC Chattanooga in
Chattanooga, TN.  And the name of this EchoMail "AREA:" is
TURBOARD.  (This would be an answer and question echo about the
TurBoard BBS software package.)

First, I would create a new message Forum.  To do this I would
issue a AM command, choose a name for the forum (say "SUPPORT")
and enter a brief description.  Okay, now I want to join that
forum with the J SUPPORT command.

Once I have the SUPPORT forum as the active forum, I issue the
CH command to bring up the chairman utilities.  I choose the
option named "Mail type" (it currently says "Normal"), and then
choose E for FidoNet Echo.

Now, I choose the option to give the system the name of the echo
area (it will say: SUPPORT).  I want to change this to
"TURBOARD" since that is the name that FidoNet calls it (so
TBFIDO.EXE will know where to put those messages).  I also want
to set up the address of the other echomail members I am
responsible for sending and getting this echo from.

I choose the last option and add the address:

  Zone: 1
  Net: 362
  Node: 614
  Point: 0

I do this because this is the address of PC Chattanooga, and I
want to get all the messages from that BBS system as well as
address my new messages to it.

Once I've done this, all I need to do is inform PC Chattanooga
that I'm ready for the echo to be sent to me!  The same
procedure can be followed for ANY FidoNet echo.

Customizing Your Displayed Screens

A fairly recent addition to TurBoard is the support to
completely customize your File Directory screen as well as the
Forum Directory screen.  (I'm sure not everyone likes the way I
like to display theinformation!)

Here are the files you can alter, their format and their
function:

(All of these files should be in your "TEXT" TurBoard
subdirectory.  Also, none of these files have extensions [that
stuff after the .])

WELCOMEN, WELCOMEG and WELCOME  -  This is the initial logon
screen that is displayed just after the "Do you want to use ANSI
terminal emulation?  " question.  WELCOMEG is the ANSI version
of this file which should be edited with an ANSI editor (I
suggest THEDRAW).  WELCOME can be edited with the internal
turboard editor, and I suggest doing this if you don't want to
mess with the different ANSI codes (at least until a time when
you want to dive into it.)

WELCOMEN is a new edition, this is the NAPLPS welcome screen.
You will need an editor to create the file (SHARENAP.ZIP), but
once you have created the file, simply rename it to WELCOMEN and
copy it in the TEXT directory, this is you 'NAPLPS log on screen.

LOGOFFN, LOGOFFG and LOGOFF  -  These are the logoff screens
that your system will display when the user issues the G
command, just before they are disconnected.  The naming
convention is the same used with WELCOME.

To edit the WELCOME file (and get ANSI colors with out going to
the WELCOMEG file) use the internal TurBoard command EDIT.  For
example:

> edit text\welcome.     [you need to add the period so turboard
will know you are specifying a file]

NEWUSERN, NEWUSERG and NEWUSER  -  This is the information that
TurBoard displays when a user logs on for the first time.  Just
before the normal questions are asked to complete the on-line
information, the user is asked, "Do you agree with the above
conditions?  ".  This file will outline those conditions you
want to place.  This would also be a good place for a legal
disclaimer, which I highly suggest.

As before, use an ANSI editor (like TheDraw) to edit the
NEWUSERG file and you may use the internal TurBoard editor for
the NEWUSER file (ex: > edit text\newuser.)

DIRN, DIRG and DIR  -  These two files are completely optional.
In fact they are not included in the TurBoard distribution ZIP.
These were included so that you may add your own personality to
your File Directory listing.  When one of these files is placed
in the TEXT subdirectory, it overrides TurBoards internal File
Directory screen.

There are a couple of quirks, and I'll outline them now.  The
Sysop never sees the finished product of DIRG and DIR.  This is
because he needs to see what is really out there (things
change).  If youwish to see what these files look like
displayed, use the TYPE command.

Ex: > type text\dirg.  [this will display the DIRG file as your
users would see it.]

Now, as before, the DIRG is reserved for ANSI codes hard coded
into the file, where the DIR file can be edited by the TurBoard
editor (see examples above).  BUT REMEMBER, if you wish to do
this, it is your responsibility to keep the DIRG and DIR file
correct and up to date.  If your system is like mine, your
directories will come and go and the numbering will change all
the time.  You need to reflect those changes in the DIRG and DIR
file.  This is why the Sysop will always see the normal TurBoard
listings.

(A quick side note:  I find it useful to create a dummy user
name that I log onto with to see what the system looks like to
the end user, I find it very helpful.  Just pick a name and log
on, you may even want to enter a message to yourself.)

FORUMN, FORUMG and FORUM  -  These files are along the same
lines as DIR and DIRG.  The sysop will never see them in their
used form, rather, he must use the TYPE command to see it.  As
before, FORUMG is the ANSI version.  If you want to keep
everything in the system, use the TurBoard editor to create/edit
the file FORUM, and here you may add colors, if you choose to.

Ex: > edit text\forum.

Again, it is the SYSOPS responsibility to keep these files
updated if he plans to use it.  TurBoard normally keeps the
menus updated, but does not update these files.

NAPLPS Color Graphics

If you have ever signed on prodogy, you have seen NAPLPS at
work.  The idea is to provide exciting color graphics to the age
old BBS technology.  Here is a brief description of what we are
talking about:

The North American Presentation-Level Protocol Syntax  (NAPLPS)
standard defines a text and graphics transmission interface with
display or recording devices with sufficient local intelligence
and memory to process the NAPLPS data stream.

In many respects, NAPLPS has reversed the normal progression
from functinal description to data format or language building.
Instead, NAPLPS starts with the code extension technique
specified by ISO 2022-1982, ANSI X.41-1974, and CSA
Z243.35-1976, and fits a versatile picture-definition standard
into the constraints of the 32 character C sets and 94-character
or 96-character G sets established by those standards.

A major advantage of the code-extension technique is, of
course,that large amounts of information can be transmitted over
narrow-bandwidth transmission lines, provided the receiving
device is capable of expanding on the information.

In case you didn't understand the above, don't worry!  All you
reall need to understand is that NAPLPS is a way to transmitting
compressed color graphics pictures that are hardware
independent.  To create these images, you will need a NAPLPS
editor (there is a shareware one on PC Chattanooga called
SHARENAP.ZIP).

Another limitation is that the caller has to have a terminal
emulation program capable of decoding the NAPLPS codes.  (One
shareware program is NAPCOM.ZIP.)  Right now, there are not many
NAPLPS terminal emulation programs, but depending on the success
of TurBoard and other NAPLPS programs, this may soon change.

DAILY.BAT (The Daily Batch Event)

Many game doors require that you run a maintainance utility once
per day.  DAILY.BAT is TurBoards way of accomplishing this.
After midnight, at the first idle moment, TurBoard executes this
.BAT file.  It is the Sysop's responsibility to include the
commands to run their particular application.

DAILY.BAT comes pre-configured to automatically pack all the
message forums with the TBFIDO.EXE program.  (Using the -P pack
mail switch.)  This takes responsibility away from the Sysop to
maintain the message forums.  You may also with to run other
programs such as a bulletin generator.

Nothing besides the file itself is required to run DAILY.BAT.
(TurBoard must have been started with TB.BAT or TBFN.BAT).

TurBoard Terminal Emulation

TurBoard has a built in NAPLPS terminal emulation mode, so that
busy Sysop's don't have to take their board down to call another
BBS system.  From the call waiting screen, type Alt-T, this will
start TurBoard's built-in terminal emulation mode.

There are several keys you should be aware of in TurBoard's
terminal emulation mode.  They are Alt-X to exit back to the
call waiting screen, Alt-C will put your terminal in ANSI mode
and clear the screen, PgUp will start a ZModem upload, PgDn will
begin a ZModem Download.

All the NAPLPS functions that are available in the normal
TurBoard BBS System are available in the terminal mode of
TurBoard.  Plans for terminal emulation mode is use of the
on-line BBS list for a dialing directory.  If you have any
suggestions for improving the Terminal Mode of TurBoard, please
let me know!

Registered TurBoard BBS's  (in order of registration)

The Haven (sysop Steve King) in Ringgold, GA (404/000-0000)
Steve owns Design Systems, a computer consulting firm
(404/861-1064) dealing in sales, service, rentals and leasing.
He is a friend and I appreciate his early support.

Portable Panic (sysop David Gridley) in Rochester, NY
(916/254-7332)  David is the one who introduced me to NAPLPS.
He is much more current in the BBS world than I am, and I am
grateful for all his help.  David runs a very current and
maintained system and is a constant supply of good ideas.  He
has helped me stay on track with TurBoard and is probably it's
most vocal supporter.  Thanks, David!

Poor Man (sysop Don Vickers) at WAFB, MO (816/563-5558)  Don is
about to move at the end of May, 1992, so you might check future
editions of this document for the correct phone number.

Mind's Eye (sysop Paul Erkkild) in Rochester, NY (716/427-7637)
Paul runs TurBoard under Windows 3.1.  It's a good thing
Microsoft added graphics support for windowed DOS sessions!

International Multimedia (sysop Ed Pimentel) in Atlanta, GA
(404/498-4254)  Ed has been a NAPLPS supporter for a long time.
Hopefully, TurBoard will live up to his expectations!

Underground Monorail (sysop Brian McCord) in Dayton, TN
(615/365-7570)  Brian is primarily responsible for the DOors
option and has contributed a lot of good ideas to TurBoard.

(your name here!)

TurBoard Phone Support

Once you've registered TurBoard, you are entitled to free phone
support at 615/756-8220.  I hope you enjoy using TurBoard as
much as I've enjoyed programming it!  And remember, if you have
a suggestion or new idea, please give me a call or leave me a
message because I want to make TurBoard the best!

That's the end of the TurBoard documentation!  I hope it was
helpful, and please support this starving programmer by sharing
this program with your friends and businesses!

TurBoard v0.40

SKIP - Skip this forum
NEXT - Go to next forum
#### - read number
+    - read in forward mode
-    - read in reverse mode
K    - Kill previous message
FIX  - Alter previous message

1     Mail>X      OK if user has mail waiting.
2     Logons>X    OK if user has called more than X times
3     Logons=X    OK if user has called exactly X times
4     Logons<X    OK if user has called less than X times
5     LastOn<X    OK if last date on < X value
6     SecLvl>X    OK if security level > X
7     SecLvl=X    OK if security level = X
8     SecLvl<X    OK if security level < X
9     expert mod  OK if expert mode is turned off
10    ANSI        OK if ANSI mode is on
11    NAPLPS      OK if NAPLPS mode is on
12    NONE       OK if not in ANSI or NAPLPS mode (ASCII Mode)
13    ANSI/ASCII  OK if either ANSI or ASCII mode
14    Birthday    OK if today is user's birthday
15   Random    OK if CheckValue is > random number between 1 and
100.

 Black                128
  Blue                 129
  Cyan                131
  Red                  132
  Magneta           133
  Brown              134
  LightGray        135
  DarkGray         136
  LightBlue         137
  LightGreen       138
  LightCyan        139
  LightRed          140
  LightMagneta  141
  Yellow        142
  White          143

  Black            144
  Blue              145
  Green            146
  Cyan             147
  Red               148
  Magneta        149
  Brown           150
  LightGray      151
 Attributes Off       152
  Underscore          153
  Blink On             154
  Invisible              155
  Clear Screen         12
  Line Feed      <none>
  End of Parag.       13